add FORBIDDEN to token stub tests #1982
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
evanugarte
approved these changes
Jan 4, 2026
charred-70
approved these changes
Jan 4, 2026
Contributor
charred-70
left a comment
charred-70
left a comment
There was a problem hiding this comment.
Waow waow W adarshmellow
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
right now we can only stub tokens to be good (OK) or bad (UNAUTHORIZED), which ignores the possibility that a token is valid but possesses invalid access level (FORBIDDEN would be expected here). this PR allows for tokens to be mocked to return FORBIDDEN status